8275 Model 416 High Performance Ethernet Workgroup Switch
User's Guide
Document Number GC30-4026-01
| Note |
|---|
|
Before using this information and the product it supports, be sure to read Appendix A, "Safety Information" and Appendix B, "Notices". |
Second Edition (August 1999)
This edition applies to Release 1.1 of the IBM 8275 Model 416 High Performance Ethernet Workgroup Switch.
Order publications through your IBM representative or the IBM branch office serving your locality. Publications are not stocked at the address given below.
A form for readers' comments appears at the back of this
publication. If the form has been removed, address your comments
to:
Department CGF
Design & Information Development
IBM Corporation
PO Box 12195
Research Triangle Park NC 27709
U.S.A.
When you send information to IBM, you grant IBM a nonexclusive right to use or distribute the information in any way it believes appropriate without incurring any obligation to you.
© Copyright International Business Machines Corporation 1999. All rights reserved.
Note to U.S. Government Users -- Documentation related to restricted rights -- Use, duplication or disclosure is subject to restrictions set forth in GS
A ADP Schedule contract with IBM Corp.
Troubleshooting and Obtaining Service
Appendix A. Safety Information
Appendix C. Cable Pinout Diagrams
Appendix D. Interface Conventions for the Console
Appendix E. Introduction to Virtual LANs (VLANs)
This guide briefly describes the features and capabilities of the 8275 Model 416 High Performance Ethernet Workgroup Switch. However, its primary purpose is to describe how to use the capabilities offered by the switch to configure, obtain status information, and monitor performance of the switch in your network.
This guide is intended for the network administrator or person responsible for integrating, maintaining and monitoring the switch in your network. The person responsible for coordinating installation and service for the switch will also find this manual useful.
This guide contains the following chapters and appendixes:
Softcopy versions of 8275-416 product documentation are available from either the Documentation CD-ROM (shipped with the product) or the IBM Networking Products Web site. To access product documentation shipped on the CD-ROM, follow the instructions in the booklet that accompanies the CD-ROM. Visit the following Web site to access the 8275-416 documentation at:
http://www.ibm.com/networking/support/docs.nsf/8275docs?OpenView
To obtain support information, including technical tips, current product information, and code updates and fixes for the switch, visit the IBM Networking Tech Support page at:
http://www.ibm.com/networking/support
You may also subscribe to receive e-mail notifications about code updates, tips, and FAQs for your switch.
If you need assistance in troubleshooting or you need service for your 8275-416, call IBM at:
Refer to your IBM Warranty for information concerning service for the product.
Changes in this revision are indicated with revision bars in the left margin and reflect:
This chapter briefly describes the functions, capabilities, and benefits of the 8275 Model 416 High Performance Ethernet Workgroup Switch. This information helps you to plan for and use the switch in your network.
Fast Ethernet switching continues to evolve from high-end backbone applications to desktop-switching applications. The switch provides a low-cost and powerful Layer 2 switch solution. It is an attractive base switch offering with the following key functions:
As a network administrator, you have a choice of three easy-to-use management methods: VT100 terminal interface, Web-based, and Simple Network Management Protocol (SNMP). These management methods enable you to configure, manage, and control the switch locally or from anywhere on the network.
The Spanning Tree Protocol (STP) provides fault tolerance on the network.
This section describes the functional support included in the switch:
The 8275-416 is a Layer 2 Ethernet switch in which frame forwarding is based on MAC addresses and VLAN membership. The switch supports the IEEE 802.1D (1998) and 802.1Q standards.
The switch supports 802.3x flow control, which, when enabled, allows the transmission of data frames to be inhibited for a specified period of time. The default for 802.3x flow control is Disabled. 802.3x flow control is valid only when the port is in full-duplex mode.
The switch detects broadcast storms and automatically blocks broadcast traffic to minimize the impact of the broadcast storm on the rest of the network. You can enable or disable this function at a switch level. If broadcast storm recovery is enabled, each port will monitor incoming broadcast traffic. If the broadcast traffic exceeds 20 percent of the port speed, the broadcast traffic on this port is blocked until the broadcast traffic returns to 10 percent or below port speed. The default for broadcast storm recovery is Disabled.
The switch port MAC addresses are stored in the forwarding database. An address learned by the switch is removed from the forwarding database after a period of time if no frames have been received from that address. The default value for the aging period is 300 seconds (5 minutes), but it can be changed by the user. The time values range from 10 seconds to 600 seconds.
The switch forwarding database stores 12 000 entries. When the database is full, no new entries are learned until an existing entry ages out. All frames with unknown destination addresses are multicast to all ports in the appropriate VLAN.
The switch supports VLANs. Appendix E, Introduction to Virtual LANs (VLANs) provides an introduction to VLANs. It describes concepts and terminology, as well as, the benefits of using VLANs. The switch is manageable only through the ports which are members of the Default VLAN (VLAN 1).
Figure 34 and Figure 35 show examples of the panels and descriptions of the parameters used to configure VLANs and add VLANs.
| Note: | The switch is manageable using the Ethernet network only through the ports which are members of the Default VLAN (VLAN 1). |
You have a choice of these easy-to-use management methods:
Accessing the switch describes how to access the switch using this interface and Using the Terminal Interface instructs you about using this interface.
Accessing the switch describes how to access the switch using this interface and Using the Web Interface instructs you about using this interface.
User access security can be implemented using the following functions of the 8275-416:
The switch:
High performance, Layer 2 switching for the switch consists of:
The 8275-416 is Y2K compliant.
When used in accordance with its associated documentation, it is capable of correctly processing and/or receiving date data within and between the 20th and 21st centuries providing all other products (for example, hardware, software, and firmware) used with the switch properly exchange accurate date data.
For additional information about Year 2000 related topics, visit:
http://www.ibm.com/year2000
Ethernet cables are not provided and must be separately purchased. You can order them through your IBM representative.
Table 1 shows cable type and length requirements. Cable
requirements depend on the speed of the network. Cables and connecting
hardware must meet the standards specified in the ANSI/TIA/EIA 856-A or CSA
T529 standards.
Table 1. Ethernet cable requirements
| Ethernet Type | Cable Requirements | Max. Cable Length |
|---|---|---|
| 10BASE-T | Category 3, 4 or 5 100-ohm STP/UTP cable | 100 m (328 ft) |
| 100BASE-TX | Category 5, 100-ohm STP or UTP cable and connecting hardware | 100 m (328 ft) |
| 100BASE-FX | 62.5-micron multimode fiber (MMF) cabling | 2 km (6561 ft) at full- duplex; 412 m (1352 ft) at half-duplex |
Do not use telephone extension cables in 10/100BASE-TX networks. The wire pairs in those cables are not twisted and the cables do not meet other requirements for use in a 10BASE-T network.
For connections to 10/100BASE-TX networks, you can use only Category 5 STP or UTP cables.
Figure 1. Front panel of the switch.
|
See Accessing the switch for more information about connectivity.
Switch LEDs are shown in Figure 2 and LED status is explained in the table that follows:
Figure 2. LEDs for the switch.
 |
Table 2. LED status for the switch.
| LEDs | Explanation | ||
|---|---|---|---|
| I (Green) | OK (Green) | Fault (Yellow) | |
| Off | Off | Off | No power is present, or there is a power supply failure. The switch is not operational. |
| On | On | Off | The switch is operational. |
| On | Blinking | Off | Configuration file or Operational Code file transfer is in process. Do not power-off or reset the switch. |
| On | Off | On | There is a hardware fault. The switch is not operational. |
| On | Off | Blinking | Diagnostics are in process. The switch is not yet operational. |
| Note: | Any other state of the LEDs indicates an LED failure. |
The single-digit display (shown in Figure 2) displays characters while diagnostics are running after
power is applied to the switch. At the successful completion of
diagnostics, the unit number appears in the display (for example, "1"
indicates Unit Number 1). Table 3 gives the meaning of other digits that can be displayed and
the corrective actions required.
Table 3. Problem indications on the single-digit display when the Fault LED is ON.
| Character | Problem | Corrective Action |
|---|---|---|
| d | Board RAM problem | Replace the switch. |
| 3 | Detected an unsupported feature module. | Remove the feature module and update the operational code, or the feature module is not fully seated in its connector. |
| 4 | PIF fault on the feature module or base board. | If feature module Fault LED is On, remove the feature module. If no feature module Fault LED is On, replace the switch. |
| 5 or 6 | Non-volatile memory problem. | Replace the switch. |
| 7 | Switch memory problem. | Replace the switch. |
| 8 | Base board loopback problem. | Replace the switch. |
| 9 or a | Feature module loopback problem. |
|
The switch has 16 base 10/100BASE-TX ports. LED status for these 16 base ports are shown in Figure 3 and they are explained in Table 4.
Figure 3. LEDs for the base 10/100BASE-TX ports on the switch
 |
Table 4. Status of LEDs for 16 base 10/100BASE-TX ports
| LED | Color | State | Explanation |
|---|---|---|---|
| Right Ethernet Port LED | Green | ON | Indicates a 100-Mbps port. |
|
| OFF | Indicates a 10-Mbps port. | |
| Left Ethernet Port LED | Green | ON | The link is up. |
|
| OFF | The link is down. | |
|
| Blinking | Transmitting (Tx) and Receiving (Rx) traffic. | |
Each feature module has an OK and a Fault LED located at the left side of the faceplate. The OK LED is green and the Fault LED is yellow. LED locations are shown in Figure 4, Figure 5, and Figure 6; LED status of the feature modules are explained in Table 5, Table 6, and Table 7.
Figure 4. LEDs for the 8-port 10/100BASE-TX feature module.
 |
Table 5. Status of LEDs for 8-port 10/100BASE-TX feature module
| LED | Color | State | Explanation |
|---|---|---|---|
| OK | Green | ON | There is power to feature module. |
|
| OFF | There is no power to feature module, no power to the switch, or the module has failed. | |
| Fault | Yellow | ON | There is a module fault. |
|
| OFF | There is no module fault. | |
| Right Ethernet Port LED | Green | ON | Indicates a 100-Mbps port. |
|
| OFF | Indicates a 10-Mbps port. | |
| Left Ethernet Port LED | Green | ON | The link is up. |
|
| OFF | The link is down. | |
|
| Blinking | Transmitting (Tx) and Receiving (Rx) traffic. | |
Figure 5. LEDs for the 8-port 100BASE-FX feature module.
 |
Table 6. Status of LEDs for 8-port 100BASE-FX feature module
| LED | Color | State | Explanation |
|---|---|---|---|
| OK | Green | ON | There is power to the feature module. |
| OFF | There is no power to the feature module, no power to the switch, or the module has failed. | ||
| Fault | Yellow | ON | There is a module fault. |
| OFF | There is no module fault. | ||
| Port LED | Green | ON | Link is up. |
| OFF | Link is down. | ||
| Blinking | Transmitting (Tx) and receiving (Rx) traffic. |
Figure 6. LEDs for the 4-port 100BASE-FX feature module.
 |
Table 7. Status of LEDs for 4-port 100BASE-FX feature module
| LED | Color | State | Explanation |
|---|---|---|---|
| OK | Green | ON | There is power to the feature module. |
| OFF | There is no power to the feature module, no power to the switch,or the module has failed. | ||
| Fault | Yellow | ON | There is a module fault. |
| OFF | There is no module fault. | ||
| Port LED | Green | ON | Link is up. |
| OFF | Link is down. | ||
| Blinking | Transmitting (Tx) and receiving (Rx) traffic. |
Table 8 summarizes the physical characteristics for the
switch:
Table 8. Summary of physical characteristics for the switch
This chapter explains the types of connections that you can use to physically access the switch. Once the connection is established, you will configure the IP information (either through the terminal interface or through DHCP or BootP), and then choose which user interface you want to use to manage it. Therefore, all interfaces support configuring the switch and obtaining information from it, thus providing greater flexibility in how you manage your switch.
There are two connection methods used to physically access the switch:
Table 9 outlines the user interfaces that are available depending on your method of connection.
Table 9. Connection methods and available user interfaces
Out-of-band connection lets you access your switch through the serial EIA 232 port. It can be either through a locally attached PC running VT100 terminal emulation software, or through a remotely attached PC running VT100 terminal emulation software connected to a modem.
To establish out-of-band connectivity using a locally attached terminal, make the physical connections and set up using the following procedure:
Figure 7. Out-of-band connectivity - locally attached terminal
 |
To establish out-of-band connectivity using a remotely attached terminal, make the physical connections using the following procedure:
Figure 8. Out-of-band connectivity - remotely attached terminal
 |
To configure the IP information, see Configuring your switch for details.
| Note: | To use in-band connectivity, you must configure the switch with its IP information (IP address, subnet mask, and default gateway), and have a path available through the Default VLAN (VLAN 1). See Configuring your switch for configuring BootP or DHCP and IP information for your switch. |
In-band connectivity allows access to the switch using the data network (as shown in Figure 9).
 |
Telnet console management can be performed through an Ethernet port (in-band connection). You must configure an IP address before using Telnet console management (Refer to Configuring your switch for initially configuring IP information for your switch.
You can use any Telnet application that emulates a VT100 terminal to establish a Telnet console management session. Up to five concurrent Telnet sessions are supported. For security, the Telnet session can be automatically logged off after a certain time of inactivity. You can configure the time of inactivity from 0 to 160 minutes; the default is 5 minutes.
The terminal interface is menu-driven and can be used to manage the switch through the EIA 232 port or a Telnet session. For security, a login user ID and password are required. Multiple user IDs and associated passwords can be created. Two levels of access privileges are supported: read/write and read only.
See Appendix D, Interface Conventions for the Console for a description of the terminal keys. You may need to configure your terminal application to enable use of these keys.
See Using the Terminal Interface for a description of the terminal interface panels.
The switch has an SNMP agent that supports SNMP Version 1 which allows it to be managed by any SNMP-based application (for example, Nways Campus Manager which supports the MIBs that the switch supports). See Using the SNMP Interface for details about the MIBs supported by the switch.
The switch has a Web server that supports HTTP 1.1 or later, and HTML 4.0 or later. Your Web browser must support HTTP 1.1 or later, HTML 4.0 or later, and JavaScript(C) 1.2.
You can use the Web interface to access and change switch parameters. Menus similar to those available through the terminal interface are also displayed by the Web browser. To access the switch from a Web browser, you must have configured the IP information for the switch. You will need a valid login user ID and password. The accepted user IDs and passwords are the same as those configured for the terminal interface.
The is no specific logout command to end a Web session. The Web session will be automatically logged off after a period of inactivity. The inactivity timeout value that is configured for the Telnet session is used by the Web interface.
See Using the Web Interface for starting and using the Web interface.
After hardware installation, you must configure the IP information for your switch in order to manage the switch using in-band connection.
First, you need to decide how you will access your switch. See Accessing the switch for details about in-band and out-of-band connection. It is assumed that when you come to this chapter you will already have established physical connectivity.
IP information can be initially assigned through either:
You can configure your switch from remote locations using DHCP (Dynamic Host Configuration Protocol) or BootP. BootP (documented in RFC 951 and RFC 1542) is a bootstrap protocol used by a diskless workstation to learn its IP address, the location of its boot file, and the boot server name. The switch supports "reserved" or static DHCP, documented in RFC 1541. The DHCP or BootP server must be available through the Default VLAN (VLAN 1).
To configure the IP information remotely using DHCP or BootP:
To manually configure the IP information:
Figure 10. Configuring BootP/static DHCP and network connection (IP information).
 |
| Note: | Disabling the Web interface will not disable Web sessions that are in progress; no new Web sessions will be started. |
This section describes how to make configuration changes, apply them, and retain the changes across a power cycle of the switch. It also provides you with specific information about making configuration changes using the terminal interface, Web interface, and SNMP interface.
You make configuration changes by entering data for one or more items. Configuration changes made by one user are also seen by other users who request the same data. Be aware that information displayed may be old data if you do not request the latest information before making any changes.
After you have make a configuration change and it is accepted:
This section provides information about making configuration changes, applying the changes, and retaining the changes across a power cycle when using the terminal interface.
On the terminal interface menus, field entries that can modified are enclosed in either square brackets ([ ]) or angle brackets (< >).
Square brackets identify an item that you can change by typing in text. As soon as you begin typing, the current value of the field is erased and is replaced by the new text. You cannot perform insert or overwrite in the field. You can use the following special keys while you are editing text fields:
Angle brackets identify an item that can be changed by selecting the desired option. The following special keys are used while selecting a configuration option:
When processing data entered in a text field, all leading and trailing white-space characters are ignored (such as, space, Tab, Esc).
Once a configuration change is made and is accepted (the cursor is no longer on the field that was modified), the change is not put into effect until you select APPLY.
| Note: | To help remind you that a configuration change needs to be applied, APPLY always appears on the Command Bar. |
When you select APPLY, the following actions occur:
If you make configuration changes and then exit a panel without applying the changes, your changes may be lost. For example, the following results in losing any changes made on the panel:
| Note: | Configuration changes are not automatically retained across a reset or a power cycle. To retain changes, you must select the Save command as described in the following section. |
To save configuration changes across a reset or power cycle, perform one of the following actions:
If you select SAVE without previously having selected APPLY for recently made configuration changes, the changes are automatically applied.
If you request a switch reset without saving your configuration changes, you are prompted to save them. Reply yes to save the changes or no if you do not want to save them.
You are next prompted if you want to reset the switch. If you reply yes, the switch is reset regardless of whether you saved the changes or not.
This section provides information on making configuration changes, getting the changes put into effect, and retaining the changes across a power cycle when using the Web Interface.
On the Web pages, field entries that can be modified are displayed in a box with a white background. Depending on the field being modified, you can modify the text by either:
Until you select APPLY or SAVE, you can restore any modified values to their original values by selecting the Undo.
After you have modified the fields, select the APPLY or SAVE to process the changes. Selecting APPLY makes the changes take effect but the changes are not automatically retained across a reset or power cycle. Selecting SAVE makes the changes take effect and also results in the changes being retained across a reset or power cycle.
Before the Web Browser sends the request to the switch, the data for the fields changed are verified. If any field is invalid, an error message is displayed identifying the field that contains the error. Invalid data errors are reported one field at a time. All configuration changes must be valid before any of the changes are sent.
If you make configuration changes and then change the page without applying or saving the changes, the changes are not processed.
To save configuration changes to be retained across a reset or power cycle, select SAVE. Configuration changes can be permanently saved by either of these actions:
This section provides information on making configuration changes, getting the changes put into effect, and retaining the changes across a power cycle when using the SNMP interface.
You make configuration changes using SNMP by issuing SNMP Set commands to MIB objects that the switch supports as read/write.
When the SNMP Set is received, the switch checks the data to ensure that it is valid. If it is invalid, the SNMP error code BADVALUE is returned in the SNMP Set Response. Otherwise, the configuration change is applied.
Configuration changes made using SNMP Set commands are not automatically retained across a reset or power cycle. To get these changes retained across a reset or power cycle, issue an SNMP Set to the swDevCtrlSaveConfiguration object supported by the switch private MIB.
Your switch's configuration is written to a configuration file. Having this file available at a remote location would allow you to restore a corrupted switch configuration. System utilities allow you to upload files from the switch and download files to the switch.
From the System Utilities panel, you can select to Upload File From Switch or Download File to Switch to process a configuration file; just specify Config File as the file type on either panel. The switch must have a path available through Default VLAN (VLAN 1).
This chapter describes the switch terminal interface. The terminal interface panels are automatically refreshed every few seconds to provide you with current information.
| Note: | The panels shown in this chapter are intended to be representative and should not be assumed to be entirely accurate because they are subject to change before final shipment of the product. |
The Login panel is the first panel displayed when initializing the terminal interface. Figure 11 shows the Login panel; you need an approved user name and password to login.
Figure 11. Login panel for terminal interface
 |
The terminal interface provides a way to log out. From the Main Menu, select LOGOUT or select System Utilities Menu, then select Logout. When you have finished using the terminal interface, ensure you have saved all configuration changes before logging out.
Following a successful login, the Main Menu appears ( Figure 12). Information following in this section is arranged in the order of topics on the Main Menu.
Figure 12. Main menu for terminal interface
 |
The switch manages information about its installed hardware and software. System information contains read-only and read/write fields. The read-only fields are written when the switch is manufactured. Through configuration you can change only the read/write fields: System Name, System Location and System Contact. Changes to these fields must be saved to be effective. A reset is not necessary for the changes to be effective.
To access system information, select System Information Menu on the Main Menu. By selecting Inventory Information Menu and System Description Menu, you can view information about your switch. Figure 13 shows your system information options.
Figure 13. System information menu
 |
Figure 14 shows the Read-Only inventory information available for your switch.
Figure 14. Inventory information menu
 |
Figure 15 shows the system information for your switch.
Figure 15. System description menu
 |
Select Management Menu on the Main Menu (Figure 16) to use the management functions of the switch.
 |
To configure the IP information, select Management Menu from the Main Menu, then select Network Connectivity Configuration Menu from the Management Menu. The Network Connectivity Configuration Menu appears as shown in Figure 17.
Figure 17. Network connection configuration
 |
You must configure the following IP information to establish in-band connectivity to the switch:
| Note: | Disabling the Web interface will not disable Web sessions that are in progress; no new Web sessions will be started. |
The switch allows you to access the switch through the serial EIA 232 port. This type of connectivity is called out-of-band connection. See Accessing the switch for descriptions of ways to access the switch.
On the Main Menu, select Management Menu. From the Management Menu, select Serial Port Configuration Menu. Figure 18 shows the parameters to configure the serial EIA 232 port.
Figure 18. Serial port configuration
 |
You specify Login Timeout and Baud Rate:
If you do not want to manually configure the switch with IP information, the switch can obtain the IP information from a BootP or DHCP server. The switch must be accessible through a port which is a member of the Default VLAN ID 1. When BootP or DHCP is enabled, the switch periodically sends out requests until a response is received from either a DHCP or BootP server. The IP information in the BootP or DHCP response overlays any existing IP information in switch. The new IP information is not retained across a reset until you select Save.
| Note: | If you configure a switch with an IP address, then DHCP frames will effectively be ignored (that is, the configured IP address will have priority over the address received via DHCP). However, BootP frames will have priority over a configured IP address. A difference between BootP and DHCP frames is that DHCP frames have 0xFFFFFFFFFFFF as the destination MAC address, while BootP frames have the switch's individual MAC address as the destination address. |
To configure the DHCP server for static DHCP, you must specify an IP address that will be assigned to the switch. This IP address is mapped to the switch's MAC address. The static DHCP does not obtain an IP address from a pool of addresses on a DHCP server unless one is explicitly set up for a given MAC address. For example, In Windows NT(R), you must set up a reservation for the switch's MAC address. Assign an IP address from the pool of current addresses. Configure the router, IP address, and subnet mask for the switch's MAC address. The switch supports no other DHCP options.
For BootP, the BootP server must have the appropriate information configured for the switch. A newly installed switch broadcast a BootP request over IP when it is powered on or reset. The BootP server, using information from its BOOTPTAB file, provides the switch with configuration information.
The following is an example of a BOOTPTAB file entry containing configuration information for the switch:
8275_416_Switch_1:ht=ethernet:ha=0004ac6b0980:\
ip=10.1.7.7:gw=10.1.1.1:\
sm=255.255.255.0
8275_416_Switch_2:ht=ethernet:ha=0004ac6b09C0:\
ip=10.1.7.8:gw=10.1.1.1:\
sm=255.255.255.0
Where:
| ht | hardware type |
| ha | host hardware address |
| ip | host IP address |
| gw | gateway address list |
| sm | subnet mask |
Configuration information obtained from the BootP server is not saved unless you select SAVE. Next, configure the Network Configuration Protocol.
If you are using DHCP or BootP, you must configure the appropriate information for the switch. To do so, configure the Network Configuration Protocol as follows:
The switch has an SNMP agent that complies with SNMP Version 1 (SNMPv1). For more about the SNMP specification, see the appropriate SNMP RFCs. The SNMP agent sends traps through TCP/IP to an external SNMP manager based on your SNMP configuration. SNMP configuration for the switch includes configuring the trap receiver and SNMP community parameters, which are described in the following text.
If you do not use the default community information, you must configure the SNMP agent with a community name for the switch. A community name is a name associated with the switch and with a set of SNMP managers allowed to manage it with a specified privileged level. You can add, change or delete communities. The switch does not have to be reset for changes to take effect. Up to six communities are simultaneously supported.
Community names in the SNMP community table must be unique. If you make multiple entries using the same community name, the first entry is kept and processed and all duplicate entries are ignored.
To configure your SNMP communities, select SNMP Community Configuration Menu from the Management Menu. Figure 19 shows SNMP community information you need to specify.
Figure 19. SNMP community configuration
 |
| Note: | If the Client IP Mask is set to 0.0.0.0, a Client IP Address of 0.0.0.0 matches all IP addresses. |
To have a specific IP address be the only authenticated IP address, set the Client IP Address to the required IP address and set the Client IP Mask to 255.255.255.255. The default for the Client IP Mask is 0.0.0.0.
A community name with read-only access is restricted from viewing SNMP community and SNMP trap receiver information.
A community status of Enable/Active means that the community is active, allowing SNMP managers associated with this community to manage the switch according to its access right.
A community status of Disable/Inactive means that the community is not active; no SNMP requests using this community will be accepted. In this case the SNMP manager associated with this community cannot manage the switch until the Status is changed back to Enable/Active.
A community status of Delete means that this name will be removed from the table. The default Status values for the default private and public community names are both Enable/Active. The default value is Delete/Inactive for the 4 undefined community names.
Trap messages are sent across a network to an SNMP Network Manager. These messages alert the manager to events occurring within the switch or on the network. Up to six simultaneous trap receivers are supported.
IP Addresses in the SNMP trap receiver table must be unique. If you make multiple entries using the same IP address, the first entry is kept and processed and all duplicate entries are ignored.
To configure trap receivers, select SNMP Trap Receiver Configuration Menu on the Management Menu. Figure 20 shows the parameters you need to specify.
Figure 20. SNMP trap receiver configuration
 |
Trap receiver parameters are:
You can optionally configure which traps that the switch should generate. You do this by selecting a status for the trap condition, that is, if it is either enabled or disabled. If a trap condition is enabled and the condition is detected, the switch's SNMP agent sends the trap to all enabled trap receivers. Otherwise, no condition is detected and no trap is sent. The default Status value for all Trap Conditions is Enabled. The switch does not have to be reset to implement the changes. Cold start traps are always generated; there are no associated trap conditions.
To configure trap conditions, select Trap Menu from the Management Menu. From the Trap Menu, select Trap Flag Configuration Menu, then enable or disable trap flags.
Figure 21 shows the trap flags that you can set.
Figure 21. Trap flags configuration
 |
These are the trap conditions that can be enabled/disabled:
The switch maintains a Trap Log; it contains a maximum of 256 entries that wrap. Trap Log information is not retained across a switch reset.
Select Trap Menu from the Management Menu, then select Trap Log Menu from the Trap Menu. Figure 22 shows the entries in the trap log.
 |
Each entry contains:
To check how many traps have been generated, select Trap Menu from the Management Menu, then select Trap Log Status Menu from the Trap Menu.
You can choose to clear the trap log on this panel (Figure 23).
 |
You can perform this operation on this panel:
You can manage the switch remotely using a Telnet connection. Accessing the switch describes setting up a Telnet connection. To configure for Telnet, select Management Menu from the Main Menu, then from the Management Menu, select Telnet Configuration Menu (Figure 24).
Figure 24. Telnet configuration
 |
The following parameters are for configuring a Telnet session with the switch:
| Note: | Changing the timeout value for active sessions does not become effective until the session is reaccessed. Any keystroke will also activate the new timeout duration. |
The switch provides a ping utility that you can use to check connectivity between devices in a network. To use ping, the switch must be configured correctly for network (in-band) connection. The source and target devices must have the ping utility enabled and running on top of TCP/IP. The switch can be pinged from any IP workstation with which the switch is connected through the Default VLAN (VLAN 1) (as long as there is a physical path between the switch and the workstation). The terminal interface allows you to send one ping, three pings or a continuous ping (one every second) to the target station.
To use Ping, select Management Menu from the Main Menu. Then select Ping Menu from the Management Menu (Figure 25).
 |
You must supply this information:
Select Management Menu from the Main Menu. Then select ARP Cache Menu from the Management Menu to displays the ARP cache for the switch.
This is used to check connectivity between the switch and other devices. The ARP cache identifies the MAC addresses of the IP stations communicating with the switch. Figure 26 shows ARP Cache information.
 |
To configure the switch, select Device Configuration Menu on the Main Menu. Figure 27 shows your options.
Figure 27. Device configuration
 |
The switch allows you to set a time after which the address will timeout, and to enable/disable broadcast storm recovery and 802.3x flow control. To set these values, select Device Configuration Menu from the Main Menu and then select Switch Configuration Menu ( Figure 28).
Figure 28. Switch configuration
 |
The value you specify is:
When you specify Enable for Broadcast Storm Recovery and the broadcast traffic on any Ethernet port exceeds 20 percent of the link speed, the switch blocks (discards) the broadcast traffic until the broadcast traffic returns to 10 percent or less.
When you specify Disable for Broadcast Recovery Mode, then the switch will not block any broadcast traffic on any Ethernet port. The default is Disable.
The switch is shipped from the factory with default port settings that allow it to automatically determine the port type and speed.
See Configuring your switch for details about making and saving configuration changes.
To configure the ports, select Device Configuration Menu from the Main Menu, then select Port Configuration Menu from the Device Configuration Menu (Figure 29).
 |
You can select or change the following values:
Note that when All is specified and you specify Disable in the Admin Mode field, you lose in-band connection to the switch.
Indicates the port number.
The feature slots are Slot 1 and Slot 2. Available feature modules have 4 and 8 ports.
You can select any of the Ethernet ports as a probe to monitor forwarded traffic (not local traffic) with an external network analyzer. The selected probe port can monitor (mirror) traffic from one port. The selected probe port also receives and transmits network traffic (tagged frames) which allows a device connected to the probe port to be managed over the network (in-band connectivity). However, the device must be 802.1Q aware to be remotely managed by the switch.
The monitoring port forwards frames with a VLAN membership which matches the monitored port. The monitoring port transmits all frames as tagged. The monitoring port does not participate in Spanning Tree Protocol (STP) and is always in a forwarding state when the link is up. The monitoring port does not forward local traffic, and it does not participate in GVRP.
From the Main Menu, select Device Configuration Menu and then, select Port Monitoring Menu from the Device Configuration Menu (Figure 30).
 |
Specify values for the following parameters:
When Port Monitoring is Enabled, make sure that the monitoring port is connected to a network analyzer and not to the network itself to avoid potential problems.
The switch participates in Spanning Tree Protocol (STP). STP allows you to configure redundant paths in the switch topology. The switch automatically blocks redundant paths to prevent loops (that is, make it fault tolerant). If an active path is broken and a backup path is available, the switch finds the redundant path and enables it. Without STP, a path failure means loss of connectivity for the affected part of the network.
The switch complies with the IEEE 802.1D standard. Refer to the IEEE 802.1D document for STP specifications. The switch supports one Spanning Tree Protocol (STP) for the entire switch.
To configure the Spanning Tree Protocol for the switch, select Device Configuration Menu from the Main Menu, then select Spanning Tree Switch Configuration/Status Menu or Spanning Tree Port Configuration/Status Menu from the Device Configuration Menu (Figure 31).
Figure 31. Spanning tree switch configuration/status
 |
The following section lists and describes the STP configuration functions and related parameters.
You can configure the Spanning Tree Protocol by ports. Select Device Configuration Menu from the Main Menu. Then select Spanning Tree Port Configuration/Status Menu from the Device Configuration Menu (Figure 32).
Figure 32. Spanning tree port configuration/status
 |
The parameter values are:
Appendix E, Introduction to Virtual LANs (VLANs) provides an introduction to the terminology and concepts for VLANs. It is helpful to review this material before you define values for the parameters associated with configuring VLANs.
From the Main Menu, select Device Configuration, and then select VLAN Management Menu to begin configuring VLANs for your switch (Figure 33).
Figure 33. VLAN management menu
 |
From the VLAN Management Menu, select VLAN Summary and Configuration Menu to begin configuring your VLANs (Figure 34). Note that there are four panels on which you can define a total of 32 VLANs.
Figure 34. VLAN summary and configuration
 |
The parameters for this panel are:
If you want to add a VLAN, move the cursor to the ADD VLAN command at the bottom of the panel and press Enter. To modify an existing VLAN, move the cursor to the line containing the VLAN and press Enter. You will be presented the VLAN Configuration Menu (Figure 35).
Figure 35. VLAN Configuration Menu
 |
The parameters for this panel are:
If a monitoring port is configured, its VLAN membership always follows the VLAN membership of the port being monitored. However, the VLAN Configuration Menu always displays the monitoring port's actual configuration; this configuration will take effect when the port is no longer a monitoring port.
See Figure 36 for the GARP configuration parameters.
 |
See Figure 37 for parameters used to configure your 802.1Q ports.
Figure 37. 802.1Q port configuration
 |
This function allows you to reset VLAN configuration parameters to those default parameters provided by the factory.
See Figure 38 for an example of the panel used to reset a VLAN.
 |
To access statistics, select Statistics Menu on the Main Menu. Traffic statistics are kept by port. Details and summaries of packets broadcast, transmitted, and switched, as well as error packets and discarded packets are the types of statistics kept for your switch.
Figure 39 shows the types of statistics that you can select to view from the Statistics Menu.
After making your selection, the panels containing statistics will refresh every few seconds.
| Note: | A description for each statistic may be obtained by pressing Help on the associated Web statistics panel. |
 |
To view a summary of port statistics, select Port Summary Statistics Menu from the Statistics Menu. See Figure 40 for a summary of port statistics that are collected.
Figure 40. Port summary statistics
 |
To view detailed port statistics, select Port Detailed Statistics Menu from the Statistics Menu (Figure 41). Detailed port statistics are collected and can be viewed on four consecutive panels. To view the next panel, move the cursor to NEXT PAGE (at the bottom of each panel) and press Enter.
Figure 41. Port detailed statistics
 |
To view a summary of switch statistics, select Switch Summary Statistics Menu from the Statistics Menu. See Figure 42 for a summary of the switch statistics that are collected.
Figure 42. Switch summary statistics
 |
To view detailed switch statistics, select Switch Detailed Statistics Menu from the Statistics Menu. See Figure 43 for the detailed switch statistics that are collected.
Figure 43. Switch detailed statistics
 |
To view forwarding database information, select Forwarding Database Menu from the Statistics Menu. See Figure 44 for the forwarding database information.
Figure 44. Forwarding database information
 |
On the Main Menu, select User Account Management Menu. Figure 45 shows the data entry panel for specifying your user names, passwords, and access mode.
Figure 45. User account management
 |
The switch allows you to add and delete users and set user passwords for the switch. You are to provide the following information:
A user with read only access is restricted from accessing the SNMP Community Configuration menu, SNMP Trap Receiver Configuration menu, User Account Management menu, and System Utilities menu. When a read only user tries to modify a configuration parameter on a menu, the data is not accepted and is not processed.
The system utilities can be used only by users with read/write access. You can use the system utilities by selecting System Utilities Menu on the Main Menu. Figure 46 shows the available utilities.
To permanently save configuration changes either select F4 to save or go to the System Utilities Menu and select Save Applied Changes, as shown in Figure 46.
Figure 46. Save applied changes
 |
When you have finished using the terminal interface, ensure you have saved and applied all configuration changes before you log out. The terminal interface provides an orderly way to log out. One way is to use the LOGOUT command on the Main Menu. Another way to log out is to select System Utilities Menu from the Main menu, then select Logout as shown in Figure 47.
 |
To upload or download a file, select System Utilities Menu from the Main Menu. Then make the appropriate selection from the System Utilities Menu.
The switch can download or upload files. Downloading is the transfer of files from a remote server into the switch. Uploading is the transfer of files from the switch to a remote server.
You can retrieve configuration settings from the switch as a binary file and send a binary configuration file to the switch. This allows you to back up the configuration or to easily update the configuration of multiple switches. Additionally, you can provide a configuration file to IBM support personnel for problem determination.
The last-saved configuration used by the switch is retained after a code update or a reset.
The switch displays result messages to indicate the status of a file transfer. Table 10 and Table 11 show the messages along with explanations for each.
Table 10. Messages - while downloading files
| Message | Explanation |
|---|---|
| TFTP in progress... | The switch has initiated the file transfer with the TFTP server. |
| Can't start...previous transfer is not complete yet! | Another TFTP operation is still taking place. Only one TFTP operation can occur at a given time. This includes both download and upload operations. Wait until the previous operation completes. |
| TFTP receive complete...storing in flash... | For Code only: The file has been successfully transferred to the switch and passed all the verification tests. It is now being stored permanently in flash memory. |
| TFTP receive complete... updating configuration | For Configuration only: The switch has received the file and will verify its integrity. The file will be stored in flash if it passes the integrity checks. The switch will reset itself after storing the file in order for the newly loaded configuration to take effect. |
| File transfer operation completed successfully. | The file has successfully been stored in flash. The switch must be reset now for the new code to become operational. |
| File failed CRC check! | The switch received the file, but detected a CRC error. Because the file is corrupted, it will not be stored in flash. Try obtaining another copy of the file. |
| This file is not intended for this product! | The switch received the file, but detected that the file was not meant for the switch. The file will not be stored in flash. If this is for a code update, obtain the correct software image from the IBM Web site. If this is for configuration, make sure that the configuration file originated from a 8275-416 switch. |
| Failure while storing in flash! | The switch successfully received the file, and began storing the image in flash; however, an error occurred during the process. For code only, the flash is most likely corrupt now and new code will have to be downloaded via the bootcode utility function. For configuration, retry the download. If the file transfer still fails, contact your IBM service representative. |
| File transfer failed! | A general error occurred. The most likely cause for this message is when the switch cannot complete the TFTP operation. This may happen if you have not entered the correct IP address for the TFTP server, or if an IP address has not been set up on the switch. Check to see if your IP addresses are configured correctly. Also, make sure that you can ping the TFTP server from the Ping Menu. This error could also occur if you entered an incorrect path or file name. Check to make sure these fields match the file location on the TFTP server. |
Table 11. Messages - while uploading files
| Message | Explanation |
|---|---|
| TFTP in process... | The switch has initiated the file transfer with the TFTP server. |
| Can't start...previous transfer is not complete yet! | Another TFTP operation is still taking place. Only one TFTP operation can occur at a given time. This includes both download and upload operations. Wait until the previous operation completes. |
| Error while preparing file for transfer. | Before uploading a file, the switch must prepare that file for transfer. This message means that there was a problem either in reading the information required for making the file, or there was a problem creating the file. Contact your IBM service representative. |
| File transfer failed! | A general error occurred. The most likely cause of this message is when the switch cannot complete the TFTP operation. This may happen if you have not entered the correct IP address for the TFTP server, or if an IP address has not been set up on the switch. Check to see if your IP addresses are configured correctly. Also, make sure that you can ping the TFTP server from the Ping Menu. This error could also occur if you entered an incorrect path or file name. Check to make sure these fields match the file location on the TFTP server. |
| File transfer completed successfully | The switch successfully sent the file to the TFTP server. |
Downloading is the transfer of files from a remote server into the switch. The download operation is initiated by selecting Download File to Switch Menu on the System Utilities Menu (Figure 48). While the download is in process, you may see messages displayed. Table 10 shows messages that can appear during the download process.
Figure 48. Downloading a file to the switch
 |
Uploading is the transfer of files from the switch to a remote server (Figure 49).
Figure 49. Uploading a file from the switch
 |
The following parameters apply to uploading and downloading of files.
File path can be appended to the file name if the string is less than 17 characters. Otherwise, the File Path field will need to be used and the File Name will be appended to the File Path as is. An example would be File Path set to c:\tftp\code\ and File Name set to e1r1v1.opr.
| Note: | File Name, File Path, and TFTP Server IP Address are applicable only if the Transfer Mode is TFTP. |
You can reset the switch without powering it off. Reset means that all network connections are terminated and the boot code executes. The switch uses the stored configuration to initialize the switch. You are prompted for confirmation if you want the reset to proceed. A successful reset is indicated by the LEDs on the switch.
After selecting Reset Menu from the System Utilities Menu, you are given the choice of the resets you can request as shown Figure 50.
 |
Reset the system by indicating the particular unit as shown in Figure 51. You must identify the switch to reset. None is the default.
 |
You can reset the configuration to factory default values without powering off the switch. The factory defaults are not restored until the switch is reset. The switch is automatically reset when this command is processed. You are prompted to confirm that you want the reset to proceed.
Reset the configuration data to the factory defaults by indicating the particular unit as shown in Figure 52. You must identify the switch to reset. None is the default.
Figure 52. Reset configuration data to factory defaults
 |
You can reset user passwords to factory default values without powering off the switch. The factory defaults are not restored until the switch is reset. The switch is automatically reset when this command is processed. You are prompted to confirm that you want the reset to proceed.
Reset the passwords by indicating the particular unit as shown in Figure 53. You must identify the switch to reset. None is the default.
Figure 53. Reset passwords to factory defaults
 |
You can manage your switch through your Web browser and Internet connection. This is referred to as Web-based management. To access the switch, your Web browser must support:
This chapter explains how to access the switch Web-based management panels to configure and manage your switch.
It is important to note that there are equivalent functions in the Web interface as in the terminal interface (that is, there are usually the same menus to accomplish a task). For example, when you log in, there is a Main Menu with the same functions available, and so on. The Web login session will be automatically logged off based on the Telnet timeout settings. There are several differences between the Web and terminal interface. For example, on the Web interface the entire forwarding database can be displayed, and the terminal interface only displays 10 entries starting at specified addresses.
So, if you have read Configuring your switch and Using the Terminal Interface, navigating the Web interface will not be difficult. This chapter is a brief introduction to the Web interface.
To have Web access to the switch:
A Web interface panel for the switch Web page consists of three frames (Figure 54). Frame 1, across the top, appears a banner graphic of the switch. Frame 2, at the bottom-left displays a hierarchical-tree view. The tree consists of a combination of folders, subfolders, and configuration and status HTML pages. You can think of the folders and subfolders as branches and the configuration and status HTML pages as leafs. Only the selection of a leaf (not a folder or subfolder) will cause Frame 2 to display a new HTML page. A folder or subfolder has no corresponding Frame 3 HTML page. Frame 3, the bottom-right frame, displays the currently selected device configuration status or the user configurable information that you have selected from the tree view of Frame 2, or both. You can resize each of these frames. There are no fixed-sized frames.
Figure 54. Web interface panel-example
 |
| Note: | You must configure the IP address of the switch before using the Web interface. |
Follow these steps to bring up the switch Web interface:
| Note: | There is an inactivity timeout associated with a Web session. The timeout value is the same one that is used for Telnet sessions. |
The following command buttons are used throughout the Web interface panels for the switch:
The switch has an SNMP agent that supports SNMPv1. This allows it to be managed by any SNMP-based application that supports the MIBs supported by the switch. The switch SNMP agent communicates with:
The SNMP-based application must specify the appropriate community name that the switch is configured to support. Real-time trap messages can be configured to be sent to designated trap receivers. All configuration information on the switch has read/write access via SNMP. All status information is also available via SNMP.
Refer to Using the Terminal Interface for details about configuring SNMP and SNMP trap receiver.
Refer to the various SNMP RFCs that are supported because the SNMP
specification is not described in this chapter. MIBs supported by the
switch are shown in Table 12.
Table 12. MIBs Supported by the Switch.
| MIBs Supported |
|---|
| MIB-II (RFC 1213) |
| Definitions of Managed Objects for Bridges (RFC 1493) |
| IEEE 802.3 Ethernet MIB (RFC 1643) |
| RMON MIB (RFC 1757) |
| IBM 8275-416 MIB |
The latest 8275-416 MIBs can be obtained from our Web site at:
http://www.ibm.com/networking/support
| Note: | Exceptions to the 8275-416 support for the MIBs listed in Table 12 are described in the sections that follow in this chapter. |
The following are 8275-416 exceptions to the support of MIB II groups:
The switch automatically collects and provides information for the MIB II groups that it supports. There are no additional configuration parameters to enable or disable this support.
RFC 1493 defines objects for managing MAC bridges based on IEEE 802.1D-1990 standard between local areas network (LAN) segments. The following objects are 8275-416 exceptions to definitions of managed objects for bridges:
RFC 1643 defines objects for managing Ethernet-like objects. The following objects are 8275-416 exceptions to IEEE 802.3 Ethernet MIB.
The switch automatically collects and provides information for the IEEE 802.3 Ethernet MIB groups that it supports. There are no additional configuration parameters to enable or disable this support.
The RMON MIB defines objects that allow a device to act like a network traffic analyzer monitoring flows and gathering data for all traffic on the network with varying degrees of detail. It is recommended that a Remote Monitor application be used to manipulate RMON MIB objects. Unexpected results can occur if an SNMP MIB browser is used to manipulate RMON MIB objects.
| Note: | The switch only supports up to 10 history buckets per history instance. |
Many of the items needed to obtain information from a switch are not available in standard MIBs. A private MIB for the switch (referred to as the IBM 8275-416 Switch Enterprise MIB) was created for these items.
The following objects in the 8275-416 MIB are not supported by this version of code:
Whenever the above objects are accessed, the switch will return an SNMP GetResponse-PDU[2] error-status = no SuchName(2)
When you use SNMP, the interface index (ifIndex) is sometimes used to identify the specific interface being addressed. On the switch, each Ethernet port is an interface and so is the IP agent being used to manage it (which is also referred to as the Management Interface).
The total number of ifIndex values in the switch is the number of installed ports plus 1. The "1" is for the Management Interface. The port ifIndex values for the switch ports start with 1 and increment by 1 for each port physically in the box. Each ifIndex value maps, one for one, with an Ethernet port. Example scenarios:
The management interface will always have an ifIndex of 1000.
This chapter contains procedures that help you to troubleshoot problems with your switch and its connections to other devices.
Be sure you read Appendix A, Safety Information before proceeding.
To obtain support information, including technical tips, current product information, and code updates and fixes for the switch, visit the IBM Networking Tech Support page at:
http://www.ibm.com/networking/support
You can also subscribe to receive e-mail notifications about code updates, tips, and FAQs for your switch.
The switch terminal interface, Web interface, and SNMP management agent give you access to important statistics and other information about the network. To obtain these statistics, see Using the Terminal Interface and Using the Web Interface and select the appropriate panels.
If one or more devices (such as workstations) connected to a switch are unable to communicate with other devices in the network, use the following steps to start the troubleshooting process:
Use Table 13 to determine which troubleshooting procedure you should
use. Unless otherwise stated, references to the OK and Fault LEDs are
those on the switch.
Table 13. Troubleshooting Symptoms and Actions
| Symtom and LED State | Action |
|---|---|
| The Fault LED and the OK LED are Off, and the fan is not running | Go to Procedure A |
| The Fault LED is blinking. | Diagnostics are still in progress...Wait |
| The Fault LED is On and there is a "1" in the single-digit display. | Go to Procedure E |
| The Fault LED is On and there is a character other than a "1" displayed in the single-digit display. | Go to Procedure B |
| None of the devices connected to the switch can communicate, the Fault LED is Off and the Power (I) LED is On. | Go to Procedure C |
| A single device connected to the switch is having trouble communicating. | Go to Procedure D |
| A feature module Fault LED is On. | Remove and replace the feature module. |
| Note: | The term segment refers to a single cable or interconnected cables between a port and the device at the other end. |
Use this procedure if all LEDs are Off:
Use this procedure if the Fault LED is On, and there is a character other than a "1" in the single-digit display:
Use this procedure if all devices connected to the switch are having communication problems, the Fault LED is Off and the OK LED is On:
Use this procedure if one device connected to the switch is having a communication problem, the Fault LED is Off, the OK LED is On and other attached devices can communicate through the switch:
Any port failing Power-On self test diagnostics will be "diagnostically disabled" when the switch becomes operational. Ports not failing diagnostics will be unaffected and will initialize to their configured state. This fault tolerant feature allows the switch to provide levels of connectivity even in the event of hardware failures. A quick glance at the Fault LEDs allows you to determine if the switch has diagnostically disabled any ports.
If a "1" appears in the single-digit display and any Fault LED is on solid, ports have been diagnostically disabled. If a console is connected to the switch through the EIA 232 port, a list of problem ports is printed on the console immediately after diagnostics and before entering operational code. You can also examine the Port Configuration Menu accessible from the Device Configuration Menu. Any ports with an "x" in the "STP St" column have been diagnostically disabled. To isolate this problem:
There are no user-serviceable parts inside the switch chassis. All feature modules are replaceable by the user.
If you need assistance in troubleshooting or you need service for your 8275-416, call IBM at:
Refer to your IBM Warranty for information concerning service for the product, or contact the place where you purchased the product.
Danger: Before you begin to install this product, read the safety information in Caution: Safety Information--Read This First, SD21-0030. This booklet describes safe procedures for cabling and plugging in electrical equipment.
Gevaar: Voordat u begint met de installatie van dit produkt, moet u eerst de veiligheidsinstructies lezen in de brochure PAS OP! Veiligheidsinstructies--Lees dit eerst, SD21-0030. Hierin wordt beschreven hoe u electrische apparatuur op een veilige manier moet bekabelen en aansluiten.
Danger: Avant de procéder à l'installation de ce produit, lisez d'abord les consignes de sécurité dans la brochure ATTENTION: Consignes de sécurité--A lire au préalable, SD21-0030. Cette brochure décrit les procédures pour câbler et connecter les appareils électriques en toute sécurité.
Perigo: Antes de começar a instalar este produto, leia as informações de segurança contidas em Cuidado: Informações Sobre Segurança--Leia Isto Primeiro, SD21-0030. Esse folheto descreve procedimentos de segurança para a instalação de cabos e conexões em equipamentos elétricos.
Fare! Før du installerer dette produkt, skal du læse sikkerhedsforskrifterne i NB: Sikkerhedsforskrifter--Læs dette først SD21-0030. Vejledningen beskriver den fremgangsmåde, du skal bruge ved tilslutning af kabler og udstyr.
Gevaar Voordat u begint met het installeren van dit produkt, dient u eerst de veiligheidsrichtlijnen te lezen die zijn vermeld in de publikatie Caution: Safety Information - Read This First, SD21-0030. In dit boekje vindt u veilige procedures voor het aansluiten van elektrische appratuur.
VAARA: Ennen kuin aloitat tämän tuotteen asennuksen, lue julkaisussa Varoitus: Turvaohjeet--Lue tämä ensin, SD21-0030, olevat turvaohjeet. Tässä kirjasessa on ohjeet siitä, miten sähkölaitteet kaapeloidaan ja kytketään turvallisesti.
Danger : Avant d'installer le présent produit, consultez le livret Attention: Informations pour la sécurité -- Lisez-moi d'abord, SD21-0030, qui décrit les procédures à respecter pour effectuer les opérations de câblage et brancher les équipements électriques en toute sécurité.
Vorsicht: Bevor mit der Installation des Produktes begonnen wird, die Sicherheitshinweise in Achtung: Sicherheitsinformationen--Bitte zuerst lesen, IBM Form SD21-0030, lesen. Diese Veröffentlichung beschreibt die Sicherheitsvorkehrungen für das Verkabeln und Anschließen elektrischer Geräte.
Vigyázat: Mielôtt megkezdi a berendezés üzembe helyezését, olvassa el a Caution: Safety Information-- Read This First, SD21-0030 könyvecskében leírt biztonsági információkat. Ez a könyv leírja, milyen biztonsági intézkedéseket kell megtenni az elektromos berendezés huzalozásakor illetve csatlakoztatásakor.
Pericolo: prima di iniziare l'installazione di questo prodotto, leggere le informazioni relative alla sicurezza riportate nell'opuscolo Attenzione: Informazioni di sicurezza -- Prime informazioni da leggere, SD21-0030, in cui sono descritte le procedure per il cablaggio ed il collegamento di apparecchiature elettriche.
Fare: Før du begynner å installere dette produktet, må du lese sikkerhetsinformasjonen i Advarsel: Sikkerhetsinformasjon -- Les dette først, SD21-0030 som beskriver sikkerhetsrutinene for kabling og tilkobling av elektrisk utstyr.
Perigo: Antes de iniciar a instalação deste produto, leia as informações de segurança Cuidado: Informações de Segurança -- Leia Primeiro, SD21-0030. Este documento descreve como efectuar, de um modo seguro, as ligações eléctricas dos equipamentos.
Peligro: Antes de empezar a instalar este producto, lea la información de seguridad en Atención: Información de Seguridad -- Lea Esto Primero, SD21-0030. Este documento describe los procedimientos de seguridad para cablear y enchufar equipos eléctricos.
Varning -- livsfara: Innan du börjar installera den här produkten bör du läsa säkerhetsinformationen i dokumentet Varning: Säkerhetsföreskrifter-- Läs detta först, SD21-0030. Där beskrivs hur du på ett säkert sätt ansluter elektrisk utrustning.
Danger: Double-pole/neutral fusing in the power
supply. Power might present in the product unless the power cord is
unplugged.
Cuidado: Fusível bipolar/neutro na fonte de alimentação. Pode haver energia presente no produto, a menos que o cabo de alimentação esteja desconectado.
Waarschuwing:
Dubbelpool/neutraal zekering in de voedingseenheid. Er kan spanning in het product aanwezig zijn zolang de stekker in het stopcontact zit.
Pas på!
Strømforsyningsenheden; er sikret til brug ved 110 og 220
volt. Der kan være; spænding; i produktet,
medmindre netledningen er trukket ud.
VAARA: Virtalähde on varustettu kaksinapaisella sulakkeella, jossa on myös maanapa. Tuotteessa voi olla jännite, jos verkkojohtoa ei ole irrotettu.
ATTENTION : L'un des deux fusibles est sur le neutre. L'alimentation é lectrique est protégée e par fusibles sur les deux pô les (phase et neutre). Pré sence de courant possible sauf si le cordon d'alimentation est débranché.
Achtung: Zweipolige bzw. Neutralleiter-Sicherung im Netzteil. Netzstecker ziehen, um sicherzustellen, daß; keine Spannung am Gerät; anliegt.
Attenzione: L'alimentatore contiene fusibili su fasi/neutro. Puoò essere presente tensione nell'apparecchiatura se il cavo di alimentazione è collegato.
Advarsel: Topolet/nøytral; sikring i strømforsyningsenheten.; Det kan være; strø.m; i maskinen hvis ikke nettkabelen er dratt ut .
Cuidado:
Protecção (por fusíveis) bipolar com neutro na fonte de alimentação. A menos que o cabo de alimentação esteja desligado, o produto pode estar sob tensão.
Precaución: Hay una fusión de doble polo/neutro en la fuente de alimentación. El producto podría estar cargado eléctricamente a menos que el cable de alimentación esté desconectado.
VARNING: Nätaggregatet är dubbelpoligt
avsäkrat. Det kan finnas stråm i produkten sövida inte när
228;tkabeln urkopplad.
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering the subject matter in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to:
IBM Director of LicensingFor license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:
IBM World Trade Asia CorporationThe following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY, OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or program(s) described in this publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.
Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.
This information is for planning purposes only. The information herein is subject to change before the products described become available.
This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference, in which case the user will be required to correct the interference at his own expense.
Properly shielded and grounded cables and connectors must be used in order to meet FCC emission limits. IBM is not responsible for any radio or television interference caused by using other than recommended cables and connectors or by unauthorized changes or modifications to this equipment. Unauthorized changes or modifications could void the user's authority to operate the equipment.
This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.
This Class A digital apparatus complies with Canadian ICES-003.
Cet appareil numérique de la classe A est conforme à la norme NMB-003 du Canada.
This product is in conformity with the protection requirements of EU Council Directive 89/336/EEC on the approximation of the laws of the Member States relating to electromagnetic compatibility. IBM cannot accept responsibility for any failure to satisfy the protection requirements resulting from a non-recommended modification of the product, including the fitting of non-IBM option cards.
This product has been tested and found to comply with the limits for Class A Information Technology Equipment according to CISPR 22/European Standard EN 55022. The limits for Class A equipment were derived from commercial and industrial environments to provide reasonable protection against interference with licensed communication equipment.
Warning: This is a Class A product. In a domestic environment this product may cause radio interference in which case the user may be required to take adequate measures.
Zulassungsbescheinigung laut dem Deutschen Gesetz über die elektromagnetische Verträglichkeit von Geräten (EMVG) vom 30. August 1995 (bzw. der EMC EG Richlinie 89/336)
Dieses Gerät ist berechtigt in Übereinstimmung mit dem Deutschen EMVG das EG-Konformitätszeichen - CE - zu führen.
Verantwortlich für die Konformitätserklärung nach Paragraph 5 des EMVG ist die IBM Deutschland Informationssysteme GmbH, 70548 Stuttgart.
Informationen in Hinsicht EMVG Paragraph 3 Abs. (2) 2:
| Das Gerät erfüllt die Schutzanforderungen nach EN 50082-1 und EN 55022 Klasse A. |
EN 55022 Klasse A Geräte müssen mit folgendem Warnhinweis versehen werden: "Warnung: dies ist eine Einrichtung der Klasse A. Diese Einrichtung kann im Wohnbereich Funkstörungen verursachen; in diesem Fall kann vom Betreiber verlangt werden, angemessene Maßnahmen durchzuführen und dafür aufzukommen."
EN 50082-1 Hinweis: "Wird dieses Gerät in einer industriellen Umgebung betrieben (wie in EN 50082-2 festgelegt), dann kann es dabei eventuell gestört werden. In solch einem Fall ist der Abstand bzw. die Abschirmung zu der industriellen Störquelle zu vergrößern."
Anmerkung: Um die Einhaltung des EMVG sicherzustellen sind die Geräte, wie in den IBM Handbüchern angegeben, zu installieren und zu betreiben.
This product is a Class A Information Technology Equipment and conforms to the standards set by the Voluntary Control Council for Interference by Information Technology Equipment (VCCI). In a domestic environment this product may cause radio interference, in which case the user may be required to take adequate measures.
Please note that this device has been certified for business purpose with regard to electromagnetic interference. If you find this is not suitable for your use, you may exchange it for one of residential use.
Class 1 Laser Product
Laser Klasse 1
Laser Klass 1
Luokan 1 Laserlaite
Appareil à Laser de Classe 1
To IEC 825-1:1993
Class 1 LED Product
LED Klasse 1
LED Klass 1
Luokan 1 Ledlaite
Appareil à LED de Classe 1
To IEC 825-1:1993
The following terms are trademarks of International Business Machines
Corporation in the United States or other countries or both:
AIX
IBM
Nways
Microsoft, Windows, Windows NT, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.
Other company, product, and service names may be trademarks or service marks of others
This appendix specifies Ethernet and null-modem cable pinouts.
Figure 55. Straight-Through UTP Cable (RJ-45 to RJ-45), T568A
 |
Figure 56. Straight-Through UTP Cable (RJ-45 to RJ-45), T568B
 |
Figure 57. Straight-Through STP Cable (RJ-45 to IBM Data Connector)
 |
Figure 58. Crossover UTP Cable (RJ-45 to RJ-45), T568A
 |
Figure 59. Crossover UTP Cable (RJ-45 to RJ-45), T568B
 |
Figure 60. Crossover STP Cable (RJ-45 to IBM Data Connector Crossover)
 |
Figure 61. Pinout of the EIA-232 Port
 |
Figure 62. EIA-232 Null Modem Cable for Terminal with 25-Pin Connector
 |
Figure 63. EIA-232 Null Modem Cable for Terminal with 9-Pin Connector
 |
Table 14 summarizes the meaning of special keys and commands that can be used by the terminal interface. You may need to configure your VT100 terminal emulation application to recognize some of these keys.
Active keys are clearly identified at the lower portion of each panel in
the terminal interface.
Table 14. Special Keys and Commands Used with the Terminal Interface
A VLAN is defined as a group of location and topology independent devices that communicate as if they are on the same physical LAN. This means that the LAN segments are not restricted by the hardware that physically connects them; the segments are defined by flexible user groups that you create using various network management tools.
With VLANs, you can define your network according to:
Implementing VLANs has three main advantages:
With traditional IP networks, network administrators spend much of their time dealing with moves and changes. If users move to a different IP subnet, the IP addresses of each device must be updated manually.
With a VLAN setup, if a device in VLAN 1 is moved to a port in another part of the network, you only need to specify that the new port is in VLAN 1.
With traditional networks, congestion can be caused by broadcast traffic that is directed to all network devices whether they require it or not. VLANs increase the efficiency of your network because each VLAN can be set up to contain only those devices that need to communicate with each other; therefore, limiting broadcast traffic to only those segments within the VLAN.
Devices within each VLAN can communicate only with devices in the same VLAN.
Figure 64 shows a network configured with three VLANs--one for each of the departments that access the network.
Figure 64. An Example of VLANs
 |
The membership of VLAN 1 is restricted to ports 1, 2, 3, 4, and 5 of Switch A; membership of VLAN 2 is restricted to ports 4, 5, 6, 7, and 8 of Switch B while VLAN 3 spans both switches containing ports 6, 7, and 8 of Switch A and 1, 2, and 3 of Switch B.
In this simple example, each of these VLANs can be seen as a broadcast domain--physical LAN segments that are not constrained by their physical location.
The switch supports VLANs that conform to the IEEE 802.1Q VLAN standard. This specifies a standard VLAN implementation that allows operation of VLANs across a multivendor network. This provides the services of traditional port-based VLANs, but also allows true interoperability with other devices that support the 802.1Q standard. In addition, the switch supports GVRP, a protocol that automates the registration of VLANs across networks.
The switch supports up to 32 user-configured VLANs (including the Default VLAN (VLAN 1)). A port may belong to multiple VLANs. This is useful if devices on a LAN segment belong to multiple VLANs.
The switch assigns a priority of "0" to untagged frames. Otherwise, the priority specified in the VLAN tag of the frame at the originating end-station is used to determine which of two priority queues is used for frame transmission. Frames with a priority of 0 to 3 are transmitted as low priority. Frames with a priority of 4 to 7 are transmitted at high priority. The mapping from user priority to traffic class is defined in table 7-2 of the IEEE P802.1D standard
The switch supports IEEE 802.1Q standards-based VLANs. This standard describes port-based VLANs as well as the methods to propagate VLAN memberships across compliant devices using GARP VLAN Registration Protocol (GVRP). Each frame contains information about the VLAN. This information is contained in a 4-byte tag that is inserted into each frame. This tag contains information concerning the VLAN that the device belongs to.
GVRP automates the configuration of VLAN information at the switch. When using devices that support GVRP, VLANs will automatically be created on the switch based on information being passed across the network from other GVRP-enabled devices in frames referred to as GVRP PDUs. This further eases change and movement as the administrator does not need to make any configuration changes at the switch, the change will automatically be detected and the necessary VLAN port membership changes made by the switch.
The switch provides configuration options that allow the use of devices that do not support tagging or GVRP. With proper configuration, both "legacy" devices and devices that support tagging or GVRP may be used on the same network.
These configuration options are described in the following sections.
The Port VLAN ID (PVID) specifies a VLAN ID for all untagged frames received on the port. Only one PVID can be configured per port. This setting is used to determine to which VLAN the untagged frames belong as they enter the switch. The specific use of this value will be discussed later in this appendix.
The switch provides a feature that allows the automatic propagation of VLAN membership information across the network. This feature is facilitated by a new protocol called GARP VLAN Registration Protocol (GVRP) that is defined as a part of the IEEE 802.1Q standard. GVRP registration messages (PDUs) are sent across the network and received by GVRP-enabled devices (switches, adapters, and so on). This protocol allows devices to automatically join and leave VLANs. An advantage of this is that if a user moves from one network connection point to another, you would not have to manually reconfigure the switch ports to add the new switch port to the VLANs that the user belongs to.
GVRP messages are sent across the network with a group address of 0x0180C2000021. The GVRP PDUs use the the same DYAP/SSAP as Spanning Tree BPDUs. Older network analyzers often interpret these GVRP PDUs as Spanning Tree BPDUs. The switch allows you to disable the GVRP function on a switch basis or on an individual port basis.
Two VLAN types, static and dynamic are associated with the switch. As the network administrator, you can manually configure static VLANs. Dynamic VLANs are created on the switch as a result of GVRP registration messages. Consequently, a dynamic VLAN is automatically removed from the switch if it is no longer being used by other devices in the network. You can convert a dynamic VLAN to a static VLAN. Once this is done, the VLAN will remain configured on the switch until you remove it.
For each static VLAN configured on the switch, you can define the mode of participation for each port. There are three modes of participation:
When a port is configured to be included in a VLAN, the port is always a member of the specified VLAN. This is similar to port-based VLANs from other legacy products. VLAN membership of these ports will propagate across the network if GVRP is enabled. Ports should be included in a VLAN whenever VLAN membership of a port is desired to be guaranteed.
A port that is configured to be Autodetected does not initially belong to the given VLAN. However, the port may join the VLAN if a GVRP PDU is received on that port declaring membership in that VLAN. Ports may be left in Autodetect mode if the devices on the segment connected to the port all support GVRP and thus will register their VLANs with the port.
A port that is configured to be excluded is prevented from being a part of the specified VLAN. You can disable GVRP on a specific port or set of ports to ensure that they never join a VLAN by receiving and propagating GVRP PDUs.
The following section will discuss some common network configuration scenarios and how the switch should be configured to ensure proper operation.
Figure 65. Untagged device to untagged device configuration
 |
This configuration consists of two untagged "legacy" devices connected to the switch. In order for these devices to communicate, they must be members of the same VLAN. In this case, the PVID of the ports that the devices are connected to must be set to the VLAN that the devices are members of. In order to set the ports PVID, a VLAN must first be created with this VLAN ID. Additionally, both ports must be configured to untag frames for this VLAN.
After this configuration is complete, the frames from Station A will arrive at Port 1 untagged, and will then be tagged internally to the switch with the PVID (VLAN 5). These frames will be sent to port 12 which is a member of the same VLAN. Because the port is set to untagged frames for this VLAN, the tag will be removed and the frame sent to Device B untagged.
 |
In this configuration, both devices support tagging and GVRP. Both devices are configured to transmit tagged frames for VLAN 5. GVRP must be enabled for the switch and for all ports which must participate in GVRP.
When Station A attempts to communicate with Station B, VLAN 5 (that Station A is a member of) is registered at Port 1 by GVRP. Likewise, Station B registers its membership with VLAN 5 on Port 12. Note that this VLAN will be dynamic because the network administrator has not explicitly configured the VLAN on the switch. Frames arrive at Port 1 from Device A, tagged for VLAN 5. These frames are forwarded to Port 12. The frames will be transmitted out of Port 12 tagged for receipt at Station B. Note that all frames in dynamically-created VLANs are transmitted as tagged.
Figure 67. Untagged device to 802.1Q compliant device (tagging and GVRP) configuration
 |
In this configuration, an untagged device, Station A, is attempting to communicate to a tagged device that is a member of the same VLAN. The network administrator first statically creates VLAN 5 on the switch to include Port 1 in this VLAN. Port 1 is configured to transmit frames untagged in VLAN 5 because Station A cannot comprehend tagged frames. Port 1 is configured with a PVID of 5 to ensure that untagged frames received on that port are assigned to VLAN 5.
Station B is also assigned to VLAN 5, and because it supports both tagging and GVRP it will automatically register its membership to VLAN 5. Because Station B resides off of Port 12, Port 12 must be configured to be either autodetected or always included in VLAN 5. Port 12 may be configured to transmit frames as either tagged or untagged because Station B is capable of handling both.
Frames from Station A arrive at Port 1 and are tagged with a VLAN ID equal to the PVID of Port 1 (VLAN 5). The frames are then switched to Port 12, where they are transmitted out of the switch either tagged or untagged, as configured. On the return path, frames tagged with VLAN 5 will arrive at Port 12, and will be received since the port is a member of VLAN 5. The frames will be switched to Port 1, and will be transmitted as untagged, as specified by the configuration of that port in that VLAN.
If any devices on a link cannot handle tagged frames, it would be best to configure the port to transmit frames as untagged in any VLAN in which those devices participate.
Figure 68. Untagged device to 802.1Q-compliant device (tagging only) configuration
 |
The primary difference in this configuration is that Station B supports tagging, but not GVRP. As a result, VLAN membership information will not be propagated from Station B to the switch. Therefore, the network administrator must configure Port 12 to always be included in VLAN 5. If this is not done, Station B's frames will be dropped as they are received at the switch because the frame's VLAN tag does not match the port's VLAN membership set.
Once this configuration is complete, data flows as in the example above.
All addresses in the network should be unique to ensure proper communication.
The 8275-416 allows you the flexibility of configuring VLANs with identical port memberships. However, duplicate VLANs can unnecessarily waste VLAN entries and be an indication that the network design needs to be reconsidered. Too many duplicate VLANs may also lead to an oversubscription of switch resources.
The 8275-416 always guarantees resources for all 32 ports in the Default VLAN (VLAN 1). Up to 31 additional VLANs may be configured or registered with the switch, with certain restrictions.
In a switch with no feature modules (that is, with only the 16 base ports which may potentially be members of any VLAN) up to 10 ports may be included or autodetected in each of the 31 available VLANs. Phrased alternatively, the switch supports 310 individual instances of port VLAN membership distributed across non-Default VLANs in whatever fashion you choose. You can choose a configuration that "oversubscribes" the switch resources. However, unpredicted results may occur. You will be notified of potential oversubscriptions by the terminal interface message Operation succeeded. WARNING: Resources exceeded! A similar message appears if you are using the Web interface to configure your switch.
Oversubscription of switch resources due to dynamic VLAN registration cannot be predicted. Therefore, oversubscription will only be indicated during configuration if the number of statically included instances of port VLAN membership exceeds the threshold of 310.
The following configuration example indicates an acceptable configuration
for an 8275-416 with no feature modules:
Table 15. Acceptable VLAN configurations with no feature modules
| Configuration | Non-Default VLAN Port Instances |
|---|---|
| 16 ports in Default VLAN (VLAN 1)* | Not counted |
| 16 ports each in 2 other VLANs * | 32 |
| 10 ports each in 12 other VLANs | 120 |
| 8 ports each in 16 other VLANs | 128 |
| 9 ports each in 1 other VLAN | 9 |
| * Duplicate VLANs | Total 289 |
As the Table 15 shows, port membership can be distributed in many ways across many VLANs, and still not exceed the limits of the switch.
The two feature modules on the 8275-416 together have the same restrictions as the base ports of the switch. The addition of feature modules does not increase the number of non-Default VLAN port instances that can be supported by either the base ports or the two feature modules together. However, the addition of feature modules does double the number of non-Default VLAN port instances that can be supported across the entire switch, with 310 port instances distributed across the base ports and 310 port instances distributed across the feature module slots.
The limitation only exist for the number of ports used in either the top or bottom of the switch. There is no limitation using base ports and feature module ports in the same VLAN.
Although duplicate VLAN configurations can waste switch resources, there are some instances where they are useful. For instance, security concerns may be addressed by having devices on the same LAN segments belonging to different VLANs, but the VLANs having the same port membership. Another use for duplicate VLAN configurations would be if a switch is placed in the core or in an intermediate level of a network. The 8275-416 functions best as an edge device as opposed to as a core switch.